deps: Bump GitHub.Copilot.SDK from 1.0.11 to 1.0.13 - #2003
Open
dependabot[bot] wants to merge 1 commit into
Open
deps: Bump GitHub.Copilot.SDK from 1.0.11 to 1.0.13#2003dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
--- updated-dependencies: - dependency-name: GitHub.Copilot.SDK dependency-version: 1.0.13 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Contributor
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
dependabot
Bot
requested review from
bradygaster and
tamirdresher
as code owners
September 7, 2026 08:11
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updated GitHub.Copilot.SDK from 1.0.11 to 1.0.13.
Release notes
Sourced from GitHub.Copilot.SDK's releases.
1.0.13
Feature: cancellation for host-owned external tools
Host-owned external tool callbacks are now cancelled when their runtime request completes or their SDK session terminates. The cancellation primitive is idiomatic per SDK: .NET passes a request token to
AIFunction, Node.js exposesToolInvocation.signal, Go cancelsToolInvocation.TraceContext, Java cancels the returnedCompletableFuture, Python cancels the handler task, and Rust drops the handler future. Go handlers that retainTraceContextfor background work must derive a separate lifetime because the invocation context is cancelled when the request ends.Feature: declare application identity with client info
Client options now accept optional client info (application name and version, integration name and version) across all six SDKs, exposed idiomatically per language (
clientInfoin Node.js,client_infoin Python and Rust,ClientInfoin Go and .NET,setClientInfoin Java). When set, the SDK forwards it on theserver.connecthandshake so the telemetry the runtime emits on the connection is attributed to the application and its Copilot integration instead of the runtime's own build. All fields are optional, and leaving client info unset keeps the runtime's default attribution. See Client info.Feature: Node Agent Factories pagination and run notifications
The experimental Node.js Agent Factories convenience API now supports paginated run history. Existing
session.factory.listRuns()calls still return the runs array, while calls withafterSeq,beforeSeq, orlimitreturn the full page with cursor and truncation metadata.Factory
runandresumeoptions now acceptnotifyOnCompleteandlogPhaseNames. The SDK forwards these options to the Copilot CLI for new and resumed runs.Feature: selectable
ask_usersession behaviorSession create and cold resume now accept a language-specific
askUserVariantoption withlegacyandelicitationvalues. SDK sessions retain the legacy question-and-answer tool by default. Selectelicitationand provide an elicitation handler to expose the structured form-basedask_usertool.Feature: rotating session-scoped GitHub credentials
All six SDKs can now acquire short-lived GitHub credentials through a session-scoped callback. The SDK registers the callback before session create or resume, maps
initialandrefreshrequests to the owning session, and removes registrations on rollback, replacement, session close, and client close. Static per-sessiongitHubTokencredentials remain supported and are mutually exclusive with the callback.Token responses use the shared tagged token/cancelled shape and require
expiresIn, expressed as the positive number of seconds remaining when the callback completes. See github/copilot-agent-runtime#16381 for the runtime credential-authority implementation.Initial acquisition occurs during create or resume; cancellation, callback errors, and invalid credentials reject that operation instead of falling back to ambient authentication. Idle sessions refresh only before their next credential-consuming operation.
Feature: extensions can request sensitive environment variables
Copilot CLI extensions can now ask for named sensitive environment variables when they join a session.
joinSession()accepts arequestedEnvironmentVariablesoption listing the variable names the extension needs. The CLI shows a permission prompt naming the extension and the exact variables requested. On approval, only those variables reach that extension and their values are written into the extension process'sprocess.envbeforejoinSession()resolves. On denial,joinSession()rejects, the extension does not load, and its tools never reach the model.An approval is remembered against the exact set of names the user saw, so an extension that later asks for one more variable prompts again. Names that are unset, or that the CLI does not filter from extensions, are not prompted for. This is the client half of the feature; it requires a Copilot CLI that supports extension environment access, and older CLIs ignore the request and grant nothing.
Feature: early session-event subscription (Rust)
The Rust SDK can now observe every event routed to a session, starting with that session's very first routed event.
Client::prepare_sessionandClient::prepare_resume_sessionreturn an inertPreparedSessionthat owns the session's event channel, so a subscription can be installed before any protocol activity begins:Feature: session-scoped GitHub token providers
Sessions now support expiry-aware GitHub token callbacks in addition to static tokens. The SDK handles refresh requests from the runtime, so extensions always receive fresh credentials. (#2412)
Feature: Java in-process native runtime on all platforms
... (truncated)
1.0.13-preview.3
Feature: rewind support across all SDKs
Sessions can now opt into file-change tracking and conversation rewind. When
enableFileChangeTrackingis enabled, the session records which files were changed during a conversation turn. You can then list pending rewind points, preview changes, and rewind the conversation history together with any tracked file modifications. (#2321)Feature: session-scoped GitHub token providers
Sessions now support a dynamic, expiry-aware GitHub token callback as an alternative to a static
gitHubToken. The SDK maps each host request (with host, session, and reason context) to your callback, handling concurrent-session isolation automatically. (#2412)Feature: built-in plugin directory support
... (truncated)
1.0.13-preview.2
Feature: rewind support across all SDKs
Sessions can now opt in to file-change tracking so that rewinding restores both conversation history and the files that were modified. Enable it with the new
enableFileChangeTrackingsession option. (#2321)Feature: session-scoped GitHub token providers
Applications can now supply a dynamic GitHub token callback instead of a static
gitHubTokenstring. The runtime calls the callback before each token use, so short-lived tokens stay fresh across long-running sessions. (#2412)1.0.13-preview.0
Feature: rewind support across all SDKs
Sessions can now opt into file-change tracking and rewind conversation history along with tracked file changes. Enable the new
enableFileChangeTrackingsession option to allow calling rewind later. (#2321)Feature: Java in-process runtime (experimental)
The Java SDK now ships platform-native classifier JARs that load the Copilot runtime directly in-process via JNA — no separate CLI child process required. Currently available for linux-x64, Windows x64, and Apple Silicon macOS. (#2301, #2393, #2402)
Feature: permission decision context forwarding
Permission handlers can now attach
decisionContextso the runtime can attribute whether a decision came from a person, host policy, or an automated recommendation. This is additive for Node, Python, Go, .NET, and Java. Rust clients that construct or matchPermissionResult::Decisiondirectly must migrate to the new struct variant. (#2294)createAttributedPermissionResult(result, context)copilot.create_attributed_permission_result(result, context)copilot.NewAttributedPermissionResult(result, context)DecisionContexton the permission decisionPermissionRequestResult.approveOnce().setDecisionContext(context)PermissionResult::approve_once().with_context(context)Feature: built-in plugin directory support
Applications can now register a set of host-bundled plugin directories that are trusted unconditionally and loaded before any user session begins. (#2330)
Feature: extensions can request sensitive environment variables (Node)
... (truncated)
1.0.12-preview.0
Feature: rewind support across all SDKs
Sessions now support rewinding conversation history and tracked file changes. Enable file-change tracking when creating a session, then rewind to a previous checkpoint to discard later turns and restore file state. (#2321)
Feature: Java in-process Copilot CLI (linux-x64)
The Java SDK now supports an in-process connection mode on linux-x64 that loads the Copilot runtime as a native library via JNA — no separate CLI child process required. Add the
copilot-sdk-java-runtimeclassifier JAR for your platform alongside the core SDK JAR. (#2301)